According to @BitMEXResearch, ForkMonitor is running the UASF BIP-110 v0.1 Release Candidate 1 and its alert shows the BIP9 reduced_data softfork status became started at Bitcoin block height 927360 as reported by the Bitcoin Knots 29.2 UASF BIP-110 v0.1 client; Source: x.com/BitMEXResearch/status/1999142307816186005 and forkmonitor.info/nodes/btc. For traders, this confirms at least one monitored node using a UASF client is reporting a started state for the reduced_data deployment, which can be independently verified on the ForkMonitor BTC nodes page; Source: forkmonitor.info/nodes/btc and x.com/BitMEXResearch/status/1999142307816186005.

According to Samson Mow (@Excellion) on Twitter, the majority of Bitcoin Core developers did not support the User Activated Soft Fork (UASF) and reportedly cannot explain why it ultimately succeeded. This highlights the decentralized nature of Bitcoin's governance, where market consensus and user action can drive major protocol changes, independent of core developer approval. For traders, this underscores the influence of community-led initiatives on network upgrades and price volatility, as demonstrated during the SegWit activation in 2017 (source: Samson Mow Twitter, May 6, 2025). Understanding these dynamics is crucial for anticipating future movements in Bitcoin and related altcoins during similar upgrade events.